Quit Weed
Last updated 27 March 2026

Privacy Policy

This Privacy Policy explains how Quit Weed handles information through the Quit Weed mobile apps, the public website at quitweed.app, and related support communication. The goal of this document is accuracy: it is meant to describe the product as it currently exists, including its third-party SDKs, advertising, analytics, local storage, and purchase flows.

1. Operator and contact

Quit Weed is operated by Michal Janecek. Contact: [email protected].

Website: quitweed.app

2. Scope

This Policy covers:

  • the Quit Weed iOS app,
  • the Quit Weed Android app,
  • the public website at quitweed.app, and
  • support emails or similar direct communication about the product.

This Policy does not replace the privacy terms of Apple, Google, Firebase, Google Mobile Ads / AdMob, Cloudflare, or any other third-party provider that also processes data under its own policies.

3. Product design overview

Quit Weed is designed as a recovery-support and progress-tracking app that uses a mix of on-device storage, platform services, and selected third-party processors. Many core data points are stored locally on the user's device, while analytics, crash reporting, advertising, billing, and entitlement management may involve external providers.

4. Information you may provide or generate in the app

Depending on which features you use, the app may store or process information such as:

  • your quit date and progress timing,
  • usage-related inputs such as usage method, amount per dose, doses per day, scale unit, and spending inputs,
  • preferred currency and app settings,
  • notification choices and reminder-related settings,
  • feature-status flags such as onboarding completion or pro entitlement status,
  • journal entries, mood values, relapse records, and related notes if you use journal-style features available on your device/platform, and
  • the contents of emails or support messages you send.

Because Quit Weed focuses on quitting or reducing cannabis use, some of this information can reveal sensitive personal information about habits, substance use, health-related experiences, and mental state.

5. Information processed automatically

Quit Weed also relies on platform services and SDKs that automatically process certain information. Depending on platform, permissions, and feature use, that may include:

  • app interaction and usage events through Firebase Analytics,
  • crash and diagnostic data through Firebase Crashlytics,
  • advertising-related device and interaction data processed by Google Mobile Ads / AdMob in ad-supported areas of the app,
  • purchase, restore, receipt, transaction, entitlement, and subscription-status information handled by Apple, Google Play, and RevenueCat for paid features,
  • device, app-version, operating-system, language, and similar technical data needed to run, debug, secure, or improve the product,
  • notification permission state and scheduled reminder data, and
  • on iOS, your response to Apple's App Tracking Transparency permission prompt if the app shows it.

According to Google's public documentation for the latest Google Mobile Ads SDK, the SDK may automatically collect and share items such as IP address, user product interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud prevention.

6. Website data and cookies

The website is separate from the mobile app. It uses necessary browser storage for consent handling and may use optional analytics on a consent basis.

  • The site stores a local consent record so it can remember whether you accepted or rejected optional website analytics.
  • Google Analytics on the website loads only after you accept optional analytics through the cookie banner.
  • The website may still involve necessary technical processing by hosting, CDN, and security providers, including IP address and request metadata needed to deliver pages, cache assets, and prevent abuse.
  • The website may also request third-party resources or link to third-party services, which can result in those providers receiving standard browser request data under their own policies.

More detail about the website's cookie and browser-storage behavior is available on the Cookies and Website Data page.

7. How information is used

Quit Weed may use the information above to:

  • provide the app's core tracking, milestone, progress, and educational functions,
  • store and restore user settings and on-device feature state,
  • schedule and manage local notifications or reminders where you allow them,
  • show ads in the free experience,
  • enable, verify, manage, or restore paid features, including lifetime purchases and recurring subscriptions,
  • measure app or website usage and improve content, stability, and performance,
  • diagnose crashes, technical problems, fraud, or abuse,
  • respond to support requests, safety issues, or legal obligations, and
  • maintain, secure, and operate the website and app infrastructure.

8. Legal bases

Where a legal basis is required, processing may rely on one or more of the following: performing the service you requested, legitimate interests in operating and improving Quit Weed, compliance with legal obligations, and consent where required for optional processing such as website analytics, tracking authorization, or notifications.

9. Where information is stored

Much of Quit Weed's core user-entered data is stored locally on the device using platform storage such as SharedPreferences, UserDefaults, or local app databases. Additional data may be processed by third parties used for analytics, crash reporting, advertising, hosting, app distribution, and billing.

10. Third-party providers and recipients

Depending on platform and feature use, information may be processed by:

  • Apple for App Store distribution, StoreKit purchase handling, restore flows, and iOS platform services.
  • Google for Google Play distribution, Google Play Billing, Firebase Analytics, Firebase Crashlytics, and Google Mobile Ads / AdMob.
  • RevenueCat for subscription and entitlement infrastructure, including identifiers needed to associate purchases with entitlements, purchase-status handling, restore support, subscription status, and related billing metadata.
  • Cloudflare for website hosting, CDN delivery, and website security/infrastructure.
  • Email or communication providers used to receive and respond to support messages.

11. Purchases, billing, and ads

Paid features currently include a lifetime purchase option and recurring subscriptions, including monthly and yearly plans, depending on platform and store availability. Payment processing, entitlement handling, receipt validation, restore workflows, and related subscription infrastructure may involve Apple, Google, and RevenueCat under their own systems and policies.

The free experience may include advertising. Advertising partners may receive device and interaction data under their own SDK behavior and policies. On iOS, the app may also request tracking permission through Apple's App Tracking Transparency framework.

12. Data retention and deletion

Retention depends on where the information lives:

  • On-device app data: usually remains until you edit it, reset it, clear app data, delete entries, uninstall the app, or otherwise remove it from your device.
  • Journal and relapse records: if you use journal-type features, those entries generally remain on your device until you delete them or remove app data.
  • Website consent record and analytics cookies: remain until they expire, you change your choice, or you clear browser storage.
  • Support emails: may be kept as long as reasonably necessary to respond, follow up, keep records, or comply with law.
  • Third-party logs and billing data: Apple, Google, Firebase, AdMob, Cloudflare, and similar providers may keep their own records under their own retention schedules.

For many app data points, deletion is achieved by deleting local data on your device. Subscription, billing, and entitlement records maintained by app stores, RevenueCat, or other third-party providers are subject to those providers' own retention and deletion practices.

13. International processing

Some service providers used by Quit Weed operate internationally. As a result, information may be processed in countries other than your own, including countries that may have different data-protection rules.

14. Your rights

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent for certain processing. To make a request, contact [email protected].

If your request relates to data processed directly by Apple, Google, Firebase, AdMob, Cloudflare, or another third party, that provider may also require you to use its own privacy tools or support process.

15. Children and age suitability

Quit Weed is not directed to children. Do not use the product if you are below the age required by applicable law, the relevant app store listing, or another platform rule that applies to you.

16. Changes to this Policy

This Policy may be updated when the product, its third-party providers, or legal requirements change. When that happens, the date at the top of this page will be updated.